Methods and systems for graphical medicine display

ABSTRACT

Methods and systems for graphical medicine display are described. In one embodiment, prescription drug data associated with a prescription drug is accessed. The prescription drug is associated with a member. The prescription drug data includes prescription name data, prescription packaging data, prescription pill data, and dosage data. A prescription pill indicator and a prescription package indicator based on the prescription drug data are determined. A medicine display based on the prescription drug data associated with the prescription drug is generated. The medicine display includes the prescription pill indicator in association with the prescription package indicator, a prescription name indicator, and a dosage indicator. The prescription name data, the prescription packaging data, and the prescription pill data are associated with the prescription drug and the dosage data is associated with the member.

FIELD

The field relates to graphical displays, and more particularly tographical display of medicines.

BACKGROUND

Patients may consume a number of prescription drugs or other medicinesduring the course of a day or week. These patients may keep lists orother records reminding them of how and when to consume their medicines.These patients may also refer to packaging while trying to adhere todosage regimens for their medicines. It may be difficult for patients tokeep track of all their medicines, let alone for them to remember properdosage, refill, and other medicine and prescription information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example system, according to an exampleembodiment;

FIG. 2 is a block diagram of an example mobile electronic device thatmay be deployed within the system of FIG. 1, according to an exampleembodiment;

FIG. 3 is a block diagram of an example benefit manager device that maybe deployed within the system of FIG. 1, according to an exampleembodiment;

FIG. 4 is a block diagram of an example data access subsystem that maybe deployed within the mobile electronic device of FIG. 2 or the benefitmanager device of FIG. 3, according to an example embodiment;

FIG. 5 is a block diagram of an example determination subsystem that maybe deployed within the mobile electronic device of FIG. 2 or the benefitmanager device of FIG. 3, according to an example embodiment;

FIG. 6 is a block diagram of an example display generation subsystemthat may be deployed within the mobile electronic device of FIG. 2 orthe benefit manager device of FIG. 3, according to an exampleembodiment;

FIG. 7 is an example process flow illustrating a method for a generatingand displaying a graphical medicine display, according to an exampleembodiment;

FIG. 8 is an example process flow illustrating a method for a generatingand displaying a pill box display, according to an example embodiment;

FIGS. 9-12 are example displays, according to example embodiments; and

FIG. 13 is a block diagram of a machine in the example form of acomputer system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed or stored.

DETAILED DESCRIPTION

Example methods and systems for graphical medicine display aredescribed. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of example embodiments. It will be evident, however, toone of ordinary skill in the art that embodiments of the invention maybe practiced without these specific details.

A patient may be a member of a pharmacy benefit manager (PBM). The PBMmay store data regarding member usage of prescription drugs. This datamay be leveraged in order to provide a member with a graphical medicinedisplay available from a member's mobile phone, tablet, portablecomputer, personal computer, or other mobile electronic device.

In general, prescription drug and medicine data may be accessed from aPBM, for example. One or more operations may be performed on theprescription drug and medicine data to generate a graphical medicinedisplay that may include a representation of a medicine cabinet. Thegenerated display may be presented on a member's mobile electronicdevice. The medicine display may be based on the member's prescriptiondrug and medicine data, and may be customized as desired by the member.

FIG. 1 is a block diagram of an example system 100, according to anexample embodiment. The system 100 is an example environment in which agraphical medicine display may be generated and presented to a member.The system 100 includes a mobile electronic device 102 in communicationwith a benefit manager device 106 over a network 104.

The mobile electronic device 102 is used by a mobile device operator.The mobile device operator may be a member of a drug benefit plan.However, the mobile device operator may be another person operating themobile electronic device 102 on behalf of the member. Examples of suchpeople include parents, guardians, caregivers, and the like. Inaddition, non-member patients of a pharmacy may also use the mobileelectronic device.

The mobile electronic device 102 may be a stand-alone device that solelyprovides at least some of the functionality to enable the generation anddisplay of a graphical medicine display, or may be a multi-use devicethat has functionality outside of the methods and systems for generatingand displaying a graphical medicine display as described herein.Examples of the mobile electronic device 102 include an IPAD or IPHONEdevice by Apple, Inc., mobile electronic devices powered by ANDROID byGoogle, Inc. a BLACKBERRY device by Research In Motion Limited, NOKIAdevices, and netbook computers. Other types of mobile electronic devicesmay also be used. These may include, but are not limited to, tablets,portable computing devices and portable communication devices.

The network 104 by which the mobile electronic device 102 communicateswith the benefit manager device 106 may include, by way of example,Mobile Communications (GSM) network, a code division multiple access(CDMA) network, 3rd Generation Partnership Project (3GPP), an InternetProtocol (IP) network, a Wireless Application Protocol (WAP) network, aWiFi network, or an IEEE 802.11 standards network, as well as variouscombinations thereof. Network 104 may also include opticalcommunications. Other conventional and/or later developed wired andwireless networks may also be used.

The benefit manager device 106 may be a device operated by an entity atleast partially responsible for prescription drug and/or medicinemanagement of the member. While the benefit manager operating thebenefit manager device 106 is typically a PBM, other entities mayoperate the benefit manager device 106 either on behalf of themselves,the PBM, or another entity. Examples of other entities that may operatethe benefit manager device 106 include a health maintenance organization(HMO), a health insurance company, or the like. Such entities may, insome embodiments, provide a prescription drug benefit directly orthrough a PBM.

Some of the operations of the PBM that operates the benefit managerdevice 106 may include the following. A member (or a person on behalf ofthe member) attempts to obtain a prescription drug at a retail pharmacylocation where the member can obtain drugs in a physical store from apharmacist or pharmacist technician, or in some instances through mailorder drug delivery from a mail order pharmacy location.

The member may have a co-pay for the prescription drug that reflects anamount of money that the member is responsible to pay the pharmacy forthe prescription drug. The money paid by the member to the pharmacy maycome from the personal funds of the member, a health savings account(HSA) of the member or the member's family, a health reimbursementarrangement (HRA) of the member or the member's family, a flexiblespending accounts (FSA) of the member or the member's family, or thelike. An employer of the member may directly or indirectly fund orreimburse the member or an account of the member for the co-pay.

The amount of the co-pay paid by the member may vary by the benefit planof the client with the PBM. The member's co-pay may be based on a flatco-pay (e.g., $10), co-insurance (e.g., 10%), and/or a deductible (e.g.,for first $500 of annual prescription drug spend) for certainprescription drugs, certain types of prescription drugs, and/or allprescription drugs.

In certain instances, the member may not pay the co-pay or may only payfor a portion of a co-pay for a prescription drug. For example, if theusual and customary cost for a generic version of a prescription drug is$4, and the member's flat co-pay is $20 for the prescription drug, themember may only pay $4 to receive the prescription drug. In anotherexample involving a worker's compensation claim, no co-pay may be due bythe member for the prescription drug.

In conjunction with receiving the co-pay (if any) from the member anddispensing the prescription drug to the member, the pharmacy submits aclaim to the PBM for the prescription drug. The PBM may perform certainadjudication functions including verifying the eligibility of themember, reviewing the formulary to determine appropriate co-pay,coinsurance, and deductible for the prescription drug, and performing adrug utilization review (DUR) on the member. The PBM then adjudicatesthe claim associated with the prescription drug and provides a responseto the pharmacy following performance of the aforementioned functions.As part of the adjudication, the client (or the PBM on behalf of theclient) ultimately reimburses the pharmacy for filling the prescriptiondrug when the prescription drug was successfully adjudicated. Theaforementioned adjudication functions generally occur before the co-payis received and the prescription drug dispensed. However, the operationsmay occur simultaneously, substantially simultaneously, or in adifferent order. In addition, more or less adjudication functions may beperformed as part of the adjudication process.

The amount of reimbursement paid to the pharmacy by the client and/ormember may be based on the type of pharmacy network in which thepharmacy is included. Other factors may be used to determine thereimbursement amount in addition to the type of pharmacy network.

In some embodiments, a mobile application or app may be downloaded,installed, and launched on the mobile electronic device 102 to enablegeneration and display of a graphical medicine display. The mobileapplication may take advantage of hardware and/or software functionalityprovided by manufacturers of the mobile electronic device 102 and/ordevelopers of the operating system of the mobile electronic device 102.For example, the mobile application may use the SAFARI web browser onthe IPAD or PHONE device, the webkit browser on an ANDROID device, orMOBILE INTERNET EXPLORER on a WINDOWS MOBILE device. The mobileapplication may include instructions that when executed on the mobileelectronic device 102 or on the benefit manager device 106 cause amachine to change its state or perform tasks within the machine and withother machines.

The mobile electronic device 102 may be in a client-server relationshipwith the benefit manager device 106, a peer-to-peer relationship withthe benefit manager device 106, or in a different type of relationshipwith the benefit manager device 106.

The benefit manager device 106 may be in communication directly (e.g.,through local storage) and/or through the network 104 (e.g., in a cloudconfiguration or software as a service) with a database 108.

The member data 110 may include information regarding the membersassociated with the PBM. Examples of the member data 110 include name,address, telephone number, e-mail address, claim history, co-payhistory, prescription drug history, and the like. The member data 110may include an employer identifier that identifies the employerassociated with the member and/or a member identifier that identifiesthe member to the employer.

The prescription drug data 112 may include, but is not limited toprescription name data, prescription packaging data, prescription pilldata, dosage data and instructions, refill data, prescription drug labeldata, prescription drug expiration data, prescription drug adherencedata, prescription drug images (e.g., image data) and photographs (e.g.,photograph data), and pill images (e.g., image data) and photographs(e.g., photograph data).

One or more of the types of prescription drug data discussed herein mayoverlap or may be included in more than one data category. For example,the prescription drug packaging data may include information that alsomay be included in the prescription drug label data, or the prescriptiondrug image data. Also for example, the prescription name data may beincluded in the prescription drug label data.

The pharmacy data 114 may include information regarding pharmaciesassociated with the PBM. These pharmacies may be retail pharmacies.Further, the client data 116 may include information regarding clientsassociated with the PBM, which may be, for example, employers or otherorganizations.

While the member data 110, the prescription drug data 112, the pharmacydata 114, and the client data 116 are shown in FIG. 1 as being separatedata categories, the member data 110, the prescription drug data 112,the pharmacy data 114, and the client data 116 may overlap in the typesof data that may be included in each data category. For example, some ofthe prescription drug data 112 may be member specific, and may beincluded in the member data 112.

The member data 110 and/or the prescription drug data 112 may include orreflect one, some, or all of prescribed drugs or other medicines of themember. The data may reflect current prescription drugs or othermedicines, historical prescription drugs or other medicines (e.g. thatare no longer being taken by the member), and/or future prescriptiondrugs or other medicines (e.g., a prescription drug that has not yetbeen filled or an expired medicine that a member is likely to rebuy).

The prescription name data includes name and identification informationof prescription drugs that have been prescribed to the member. Examplesof the prescription name data include PRILOSEC, LIPITOR, and XANAX.Examples of identification information include a national drug code(NDC) and/or letters and numbers that may be printed on the drugpackaging or on the drug itself, or a drug classification.

The prescription packaging data includes information regarding thepackaging of prescription drugs that have been prescribed to the member.The prescription packaging data may include, by way of example, wordsappearing on a box or bottle in which the prescription drug is shipped,colors of the box, bottle, or tube holding the prescription drug,ingredient information, warning information, or manufacturerinformation.

The prescription pill data may include information regarding a pill of aprescription drug that has been prescribed to the member. Theprescription pill data may include, by way of example, a color of thepill, size of the pill, any identification numbers or letters that maybe on the pill, a potency of the pill, or a type of pill (e.g., capsuleor tablet). When the prescription drug is not in the form of a pill,other similar types information may be captured (e.g., color of aliquid) as part of the prescription pill data and/or the dosage data.

The dosage data may include information regarding a dosage of aprescription drug that has been prescribed to the member. The dosagedata may include, by way of example, a number of pills the member is totake, how often the member is to take the pills, or an amount (e.g., inmilligrams) of the prescription drug the member is to take.

The prescription drug image data may include an image of a prescriptiondrug that has been prescribed to the member. The image may be an imagecreated that resembles or is what the prescription drug package or pilllooks like. This image may be used when displaying a prescription drugpackage indicator or a prescription drug pill indicator at the mobileelectronic device 102 to the member. The prescription drug image datamay also include a standard image of what the prescription drugprescribed to the member is supposed to look like. The standard imagemay be an actual image, a similar image, or a computer generated image.

The prescription drug refill data may include a number of refills of aprescription drug that the member has left under his or herprescription. The prescription drug expiration data may include anexpiration date for a prescription drug that was shipped or sold orotherwise fulfilled to the member.

The prescription label data may include data printed on a label of aprescription drug that has been prescribed to the member. The label mayhave been custom print for the member, and may include the member'sname, type of prescription drug, dosage information, and warninginformation, among other information, some of which may be beendescribed above in connection with other types of prescription drugdata. The prescription label data may also include an image orphotograph of the label shipped or sold with the prescription drug tothe member.

The prescription drug adherence data may include data regarding themember's adherence to a treatment or dosage prescribed for the member inconnection with a prescription drug. The prescription drug adherencedata may include information regarding whether the member has beentaking the prescription drug as instructed, has been taking theprescribed dose of the prescription drug in the prescribed timeframe, orhas deviated from the prescribed treatment or dosage. The prescriptiondrug adherence data may be received from the mobile electronic device102 associated with the member, if the member inputs such informationinto the mobile electronic device 102.

The prescription drug photograph data may include a photograph of theprescription drug package or bottle taken before the prescription drugwas shipped to the member. The prescription drug photograph data mayinclude a single photograph or multiple photographs with respect to theprescription drug package. Multiple photographs may be taken from thesame angle or different angles of the prescription drug package. Thephotographs may include, for example, photographs of the prescriptiondrug label, top-down photographs of the open prescription drug bottleincluding images of the pills, or images of the pills. The prescriptiondrug image data may also include a standard photograph of what theprescription drug or pill prescribed to the member is supposed to looklike.

While the database 108 is discussed here in connection with the memberdata 110, the prescription drug data 112, the pharmacy data 114, and theclient data 116, system 100 may include multiple databases in order tofacilitate generation of a graphical medicine display. Further, eachtype of data described above may be stored in multiple databases and/ormay each include data overlapping in multiple data categories.

Certain data from the database 110 may be stored on the mobileelectronic device 102 separate from or in addition to the data stored inthe database 110. In some embodiments, the data may be stored on themobile electronic device 102 instead of in the database 110. In someembodiments, the mobile electronic device 102 is pre-loaded with certaindata.

While the system 100 in FIG. 1 is shown to include single devices 102,and 106, multiple devices may be used. The devices 102 and 106 may bethe same type of device or may be different device types. When multipledevices are present, the multiple devices may be of the same device typeor may be a different device type. Moreover, system 100 shows a singlenetwork 104, however, multiple networks can be used. The multiplenetworks may communicate in series with each other to link the devices102 and 106 or in parallel to link the devices 102 and 106.

FIG. 2 illustrates the mobile electronic device 102, according to anexample embodiment. The mobile electronic device 102 may facilitategeneration and display of a graphical medicine display. The mobileelectronic device 102 may be deployed in the system 100, or mayotherwise be used.

The mobile electronic device 102 may include a data access subsystem202, a determination subsystem 204, and/or a display generationsubsystem 206. The data access subsystem 202, the determinationsubsystem 204, and the display generation subsystem 206 may interact orexchange data in order to facilitate generation and display of agraphical medicine display.

The data access subsystem 202 may enable access to data from thedatabase 108, including the member data 110, prescription drug data 112,the pharmacy data 114, and the client data 116. The data accesssubsystem may access the name data, the prescription packaging data, theprescription pill data, the dosage data and instructions, the refilldata, the prescription drug label data, the prescription drug expirationdata, the prescription drug adherence data, the prescription drug images(e.g., image data) and photographs (e.g., photograph data), and the pillimages (e.g., image data) and photographs (e.g., photograph data). Thedata access subsystem 202 may access the data above based on changes tothe data or indicators being generated, as will be described below.

The determination subsystem 204 may enable determination of whichindicators or information are to be generated or displayed in thegraphical medicine display based on data accessed by the data accesssubsystem 202. The display generation subsystem 206 may enablegeneration and display of the indicators or information determined bythe determination subsystem 204. Each of the subsystems 202-206 mayinclude additional features and functionality, some of which will bedescribed below.

FIG. 3 illustrates the benefit manager device 106, according to anexample embodiment. The benefit manager device 106 may be deployed inthe system 100, or may otherwise be used.

The benefit manager device 106 may include the data access subsystem202, the determination subsystem 204, and the display generationsubsystem 206. In some embodiments, one or more of the varioussubsystems 202-206 when used may provide, e.g., server-sidefunctionality to the mobile electronic device 102. By way of example,the data access subsystem 202 may be deployed in both the mobileelectronic device 102 and the benefit manager device 106. The mobileelectronic device 102 may then perform some of the functionality whileother functionality is performed by the benefit manager device 106.

FIG. 4 illustrates an example data access subsystem 202 that may bedeployed in the mobile electronic device 102, the benefit manager device106, or otherwise deployed in another system. The modules arecommunicatively coupled and included in the data access subsystem 202 toenable various data access functionalities. The modules of the dataaccess subsystem 202 that may be included are a prescription drug dataaccess module 402, a dosage loading module 404, a dosage reminder module406, and adherence receiver module 408. Other modules may also beincluded.

In some embodiments, the modules of the data access subsystem 202 may bedistributed so that some of the modules are deployed in the mobileelectronic device 102 and some modules are deployed in the benefitmanager device 106. In one embodiment, the modules are deployed inmemory and executed by a processor coupled to the memory. Thefunctionality included within the modules 402-408 may be combined into alesser number of modules, further divided among a greater number ofmodules, or redistributed among existing modules. Other configurationsincluding the functionality of the modules 402-408 may be used.

In some embodiments, prescription drug data access module 402 may accessthe prescription drug data 112 associated with a prescription drug ormember. The prescription drug may be associated with a member. Theprescription drug data 112 may be any of the prescription drug datadiscussed above, including, but not limited to the prescription namedata, the prescription packaging data, the prescription pill data, andthe dosage data. The prescription name data, the prescription packagingdata, and the prescription pill data are associated with theprescription drug and the dosage data is associated with the member.

In some embodiments, the dosage loading module 404 may load or preloaddosage instructions associated with a prescription drug from the dosagedata in the database 108. Further, the dosage reminder module 406 mayload a dosage reminder for the member prescribed the prescription druginto an electronic calendar associated with the member. A single dosagereminder or multiple dosage reminders may be loaded.

The electronic calendar may be included on the graphical medicinedisplay. For example, the electronic calendar may be overlaid on thegraphical medicine display. The electronic calendar may also begenerated or rendered on an additional display, or may otherwise bedisplayed. The electronic calendar may be a calendar available from ageneral purpose calendaring and scheduling application.

Further, the adherence receiver module 408 may receive a member doseindication from the mobile electronic device 102. The member doseindication may correspond to or reflect whether the member followed oradhered to a prescription drug treatment or prescription drug dosage(e.g., a number of pills a day over a time period) associated with theprescription drug and the member. For example, if the member takes apill in the morning according to the prescription drug dosage, themember may indicate through a user interface on the mobile electronicdevice 102, that the member took the pill.

FIG. 5 illustrates an example determination subsystem 204 that may bedeployed in the mobile electronic device 102, the benefit manager device106, or otherwise deployed in another system. One or more modules arecommunicatively coupled and included in the determination subsystem 204to enable various determination functionalities. The modules ofdetermination subsystem 204 that may be included are an indicatordetermination module 502, a days remaining determination module 504, adoses remaining determination module 506, a refills remainingdetermination module 508, an adherence determination module 510, and animage comparison module 512. Other modules may also be included.

In some embodiments, the modules of the determination subsystem 204 maybe distributed so that some of the modules are deployed in the mobileelectronic device 102 and some modules are deployed in the benefitmanager device 106. In one embodiment, the modules are deployed inmemory and executed by a processor coupled to the memory. Thefunctionality included within the modules 502-512 may be combined into alesser number of modules, further divided among a greater number ofmodules, or redistributed among existing modules. Other configurationsincluding the functionality of the modules 502-512 may be used.

In some embodiments, the indicator determination module 502 maydetermine a prescription pill indicator and/or a prescription packageindicator based on the prescription drug data 112. For example, with thepackaging data, the pill data, the image data, and/or the photographdata received from the data access subsystem 202, the indicatordetermination module 502 may determine what image should be shown to themember in the graphical medicine display to represent a prescriptiondrug having been prescribed to the member.

In some embodiments, the days remaining determination module 504 maydetermine a number of days for consuming a prescription drug remainingfor the member based on the prescription drug data and the dosage data.For example, if the data access subsystem 202 accesses information fromthe prescription drug data 112, and dosage data represents that thereare 10 pills in a prescription drug package and that the member is toconsume 1 pill a day, on day 6, the days remaining determination module504 may determine that the number of days remaining is 4 days.

In some embodiments, the doses remaining determination module 506 maydetermine a number of doses of the prescription drug remaining for themember based on the prescription drug data 112 and the dosage data. Forexample, if the data access subsystem 202 accesses information from theprescription drug data 112 and the dosage data represents that there are20 doses in a prescription drug package and that the member is toconsume 2 doses per day, after day 6, the doses remaining determinationmodule 506 may determine that the number of doses remaining is 8 doses.

In some embodiments, the refills determination module 508 may determinea number of refills of the prescription drug remaining for the memberbased on the prescription drug data 112 and the dosage data. Forexample, if the data access subsystem 202 accesses information from theprescription drug data 112 and the dosage data represents that there are5 refills in a prescription and that the member has been shipped 2refills, the refills remaining determination module 508 may determinethat the number of refills remaining is 3 refills.

Further, the adherence determination module 510 may determine anadherence metric based on the prescription drug data 112 associated withthe prescription drug and the member dose indication described abovethat may be received via the adherence receiver module 408. For example,if the member dose indication represents that the member properly took 9out of 10 doses of the prescription drug, the adherence determinationmodule 510 may determine that the adherence metric for the member is90%.

Additionally, the image comparison module 512 may compare a prescriptiondrug image associated with the prescription drug to a standardprescription drug image associated with the prescription drug. Forexample, a PBM may take a photograph or keep an image of eachprescription drug package sent to a member, which may be stored with theimage data or the photograph data. The PBM may also have a standardprescription drug image of the prescription drug that may be stored withthe image data or the photograph data. The image comparison module 512may compare the photograph or image of the prescription drug sent to themember with the standard prescription drug image in order to determinewhether the proper prescription drug was sent to the member according tothe prescription.

FIG. 6 illustrates an example display generation subsystem 206 that maybe deployed in the mobile electronic device 102, the benefit managerdevice 106, or otherwise deployed in another system. One or more modulesare communicatively coupled and included in the display generationsubsystem 206 to enable various display generation relatedfunctionalities. The modules of the display generation subsystem 206that may be included are a medicine display generation module 602, adays remaining indicator generation module 604, a doses remainingindicator generation module 606, a refills remaining indicatorgeneration module 608, a label indication generation module 610, anadherence indication generation module 612, and an indication updatingmodule 614. Other modules may also be included.

In some embodiments, the modules of the display generation subsystem 206may be distributed so that some of the modules are deployed in themobile electronic device 102 and some modules are deployed in thebenefit manager device 106. In one embodiment, the modules are deployedin memory and executed by a processor coupled to the memory. Thefunctionality included within the modules 602-614 may be combined into alesser number of modules, further divided among a greater number ofmodules, or redistributed among existing modules. Other configurationsincluding the functionality of the modules 602-614 may be used.

In some embodiments, the medicine display generation module 602 maygenerate a graphical medicine display (e.g., a mobile medicine cabinet)based on the prescription drug data 112 associated with the prescriptiondrug. The medicine display may include a prescription pill indicator inassociation with a prescription package indicator. The prescription pillindicator and the prescription package indicator may be based on theprescription drug data 112. The medicine display may also include aprescription name indicator based on the prescription name data and adosage indicator based on the dosage data.

The indicators described herein may be generated as part of thegraphical medicine display, separate from the graphical medicinedisplay, added to the graphical medicine display, or may otherwise begenerated. The indicators described herein may also be rendered.

In some embodiments, the days remaining indicator generation module 604may generate a days remaining indicator. The days remaining indicatormay be included in the medicine display and may correspond to or reflectthe number of days for consuming the prescription drug remaining for themember, as may be determined by the days remaining determination module504.

Further, the doses remaining indicator generation module 606 maygenerate a doses remaining indicator. The doses remaining indicator maybe included in the medicine display and may correspond to or reflect anumber of doses of the prescription drug remaining for the member, asmay be determined by the doses remaining determination module 506.

Also, the refills remaining indicator generation module 608 may generatea refills remaining indicator. The refills remaining indicator may beincluded in the medicine display and may correspond to or reflect anumber of refills of the prescription drug remaining for the member, asmay be determined by the refills remaining determination module 508.

In some embodiments, the label indication generation module 610 maygenerate a prescription drug label indicator. The prescription druglabel indicator may be included in the medicine display and may be basedon the prescription drug label data. The prescription drug label datamay be associated with the prescription drug and the member, and may beaccessed via the prescription drug data access module 402. Theprescription drug label indicator may also be based on the image dataand the photograph data.

In some embodiments, the adherence indication generation module 612 maygenerate a prescription drug adherence indicator. The prescription drugadherence indicator may be included in the medicine display and may bebased on the prescription drug adherence metric described above.

In some embodiments, the indication updating module 614 may update theprescription package indicator in the medicine display. The update ofthe prescription package indicator may be based on an indication thatthe prescription packaging data changed. For example, a manufacturer maychange a prescription drug package style or prescription drug bottlestyle. The change may be stored in the prescription drug packaging data.An indication that the prescription drug packaging data changed may beaccessed via the prescription drug data access module 402.

Further, the indication updating module 614 may update the prescriptiondrug label indicator in the medicine display. The update of theprescription drug label indicator may be based on an indication that theprescription drug label data changed. For example, a manufacturer maychange a prescription drug label warning or color. The change may bestored in the prescription drug label data. An indication that theprescription drug label data changed may be accessed via theprescription drug data access module 402.

Updating the prescription drug package indicator and/or the prescriptiondrug label indicator in the medicine display may include generating anew medicine display to reflect that data (e.g., prescription packagingdata and/or prescription drug label data) has changed, as describedabove. Further, accessing the indication that the data (e.g.,prescription packaging data and/or prescription drug label data) haschanged may be based on or may include comparing new data to old data todetermine that there is a change.

The display generation subsystem 206 and one or more of the modules602-614 may generate a medicine display showing one or more of theindicators described above. In general, the display or screen is acomputer generated image or series of images capable of being viewed bya person when presented on a device. The display is generallygraphically rendered and presented to a device operator on a displaydevice unit (e.g., a television screen, a computer monitor, or a mobileelectronic device display) of the device.

FIG. 7 illustrates a method 700 for enabling generation and display of agraphical medicine display according to an example embodiment. Themethod 700 may be performed by the mobile electronic device 102, thebenefit manager device 106, partially by the mobile electronic device102 and partially by the benefit manager device 106, or may be otherwiseperformed.

The prescription drug data 112 may be accessed at block 702. Theprescription drug data accessed at block 702 may be any of theprescription drug data discussed herein. For example, the prescriptiondrug data accessed may be the prescription name data, the prescriptionpackaging data, or the prescription expiration data, any of which may beassociated with a prescription drug and a member.

Single or multiple prescription drug related indicators (some of whichhave been described above) may be determined at block 704. For example,a prescription label indicator and a prescription package indicator maybe determined. The prescription label indicator may be based on aphotograph (e.g., from the photograph data) of the prescription drugbefore a prescription drug order was shipped or otherwise fulfilled tothe member. Further, the prescription package indicator may be based ona photograph (e.g., from the photograph data) of the prescription drugbefore a prescription drug order was shipped or otherwise fulfilled tothe member.

A medicine display may be generated at block 706. The medicine displaymay be a mobile medicine cabinet and may include a prescription pillindicator, a prescription package indicator, or a prescription drugexpiration indicator. In some embodiments, the prescription packageindicator may be based on a comparison of a prescription drug imageassociated with the prescription drug data 112 and a standardprescription drug image associated with the prescription drug. In thismanner, it may be verified that the member was shipped the correctprescription drug.

In some embodiments, the medicine display may include a prescriptiondrug dose reminder. The prescription drug dose reminder may indicatethat the member is to follow a prescription drug treatment orprescription drug dosage associated with the prescription and themember. The prescription drug dose reminder may be based on prescriptiondrug data 112 and the dosage data.

In some embodiments, dosage instructions may be loaded or preloaded to,e.g., the mobile electronic device 102 at block 708. The dosageinstructions may be loaded or preloaded for the member associated withthe prescription drug based on the dosage data associated with themember.

In some embodiments, a plurality of dose reminders may be loaded into anelectronic calendar at block 710. The electronic calendar may beaccessed, e.g., via the mobile electronic device 102. The plurality ofdose reminders may be for the member associated with the prescriptiondrug and may be loaded into an electronic calendar associated with themember.

In some embodiments, adherence data may be received at block 712. Forexample, a member dose indication may be received. The member doseindication may correspond to or reflect whether the member followed theprescription drug treatment or prescription drug dosage associated withthe prescription drug and the member. The member dose indication may bereceived via, e.g., the mobile electronic device 102.

Further, one or more of the indicators described herein may be updatedat block 714. For example, the prescription package indicator includedin the medicine display may be updated, or the medicine display itselfmay be regenerated, based on an indication that prescription packagingdata changed. Further, the prescription drug label indicator included inthe medicine display may be updated based on an indication that theprescription drug label data changed.

Additionally, images may be compared at block 716. For example, aprescription drug image associated with the prescription drug data 112may be compared with a standard prescription drug image associated withthe prescription drug to determine if there is a drug match. In someembodiments, the prescription package indicator included in the medicinedisplay may be based on the comparison of the prescription drug imageassociated with the prescription drug data 112 and the standardprescription drug image associated with the prescription drug if, forexample, there is a drug match.

FIG. 8 illustrates a method 800 for enabling generation and display of apill box display according to an example embodiment. The method 800 maybe performed by the mobile electronic device 102, the benefit managerdevice 106, partially by the mobile electronic device 102 and partiallyby the benefit manager device 106, or may be otherwise performed.

A first drug and/or a second drug may be identified at block 802. Thefirst drug and/or second drug may be identified by determining that theyare associated with a member based on member data 110 and/orprescription drug data 112.

Pill image data may be accessed at block 804. The pill image data may beassociated with a number of drugs including the first drug and/or thesecond drug. The drugs may be associated with a member. The pill imagedata may include image data corresponding to each of the drugsassociated with the member.

Pill dosage data may be accessed at block 806. The pill dosage data maybe associated with drugs including the first drug and/or the seconddrug. The pill dosage data may include the dosage data (e.g., asdescribed above) corresponding to each of the drugs associated with themember.

A pill box display may be generated at block 808. The pill box displaymay be based on the pill image data and the pill dosage data. The pillbox display may include pill image indicators corresponding to thedrugs, including the first drug and the second drug.

In some embodiments, a member dose indication may be received at block810. The member dose indication may correspond to or reflect whether themember followed a pill dosage associated with the first drug and/or thesecond drug. The pill dosage may be based on the pill dosage data. Forexample, the member dose indication may be received via, e.g., themobile electronic device 102. The member may input the member doseindication via, e.g., the mobile electronic device 102, to indicate thata dose of the medicine was properly taken.

In some embodiments, the pill box display may be updated at block 812.The pill box display may be updated based on the member dose indication.In some embodiments, the first drug and/or the second drug may beprescription drugs.

In some embodiments, a drug adherence metric may be determined. The drugadherence metric may be based on the pill dosage data and the memberdose indication. For example, if the member was directed to take 4 pillsa day, but only indicated (e.g., via the mobile electronic device 102)that 1 pill was taken for a day, it may be determined that the drugadherence metric is 25% for the member for that day.

FIG. 9 illustrates an example medicine display 900 in accordance with anexample embodiment. The medicine display 900 may be displayed on themobile electronic device 102 (e.g., a tablet device) and shows anexample of a medicine display that may be generated in accordance withan embodiment. For illustrative purposes only, the medicine display 900is shown as being presented on a particular type of mobile electronicdevice.

The medicine display may be a mobile medicine cabinet and may beaccessible by the member whenever the member has access to the tablet.The medicine display may include, as discussed above, a number ofprescription package indicators (e.g., prescription package indicators902, 904, 906, 908). The prescription package indicators may show, e.g.,a bottle that the prescription drug may be shipped in.

Further, the medicine display 900 may include a prescription drug labelindicator (e.g., prescription drug label indicators 910, 912, 914, 916)for each prescription drug, as described above. The medicine display 900may additionally include a prescription pill indicator (e.g.,prescription pill indicators 918, 920, 922, 924) for each prescriptiondrug, as described above. Additionally, the medicine display 900 mayinclude a prescription expiration indicator 926, as described above. Theprescription expiration indicator 926 may be depicted as, e.g., cobwebs, to indicate that the corresponding prescription has expired.

In some embodiments, the medicine display 900 may include a pill boxdisplay (e.g., pill box 928), as discussed above. The pill box display928 may also be shown on its own, in some implementations, without themedicine display.

In some embodiments, the medicine display 900 may allow the user toorganize the medicine display 900 by dragging and dropping theprescription drug package indicators (e.g., prescription packageindicators 902, 904, 906, 908 of FIG. 9) to different rows orarrangements. The member may organize the medicine display 900 based onfrequency of dose, therapy, or color. Further, the member may drag anddrop the prescription drug package to the trash package 930 in order todispose of it.

Similarly, the member may drag and drop the prescription drug package tothe add package 932 to purchase (renew, refill, etc.) more of theprescription drug. The member may drag and drop the prescription drugpackage to the info package 934 to receive information about theprescription drug. The member may additionally drag and drop theprescription drug package to the price package 936 to find a price forthe prescription drug.

FIG. 10 illustrates an example popup display 1000 that may be generatedin response to receiving a selection of a prescription drug package fromthe medicine display 900 of FIG. 9. In some embodiments, and asdescribed above, the medicine display 900 may be used to collect memberusage and adherence data. For example, the member may rate one or moreprescription drugs through the medicine display 900 and the ratings maybe aggregated and provided to prescribers. The ratings (e.g., ratings1002) may provide the prescribers with more information about memberpreference and quality issues. Further, popup display 1000 may providebuttons 1004, 1006, 1008, and 1010, respectively, which, if selected,may, in response, allow the member to learn how to save money on theprescription drug, renew the prescription drug, receive a reminderregarding the prescription drug, or dispose of (trash) the prescriptiondrug from the medicine display 900, respectively.

As discussed above, a number of reminders may be provided to members toremind them to take their prescription drugs. The reminders may beprovided by email, text, device specific messaging, or by a reminderindicator on the medicine display 900. For example, if a member needs totake a dose of a prescription drug, the cap of the prescription drugimage in the medicine display may glow or change color in order to alertthe member to take the prescription drug dose.

In some embodiments, the member may interact with the reminder toprovide feedback. For example, the member may interact with the medicinedisplay 900 to skip a dosage, snooze the reminder, or confirm that thedosage was taken (e.g., adherence). Data received from this memberfeedback can be stored with, e.g., the prescription drug data 112 andcan be used for reporting adherence trends, indentifying variances, andsending feedback to member incentive programs.

FIG. 11 illustrates an example medicine display 1100 in accordance withan example embodiment. The medicine display 1100 may be displayed on themobile electronic device 102 and shows an example of a medicine displayin accordance with an embodiment. The medicine display 1100 may berendered on a smart phone and may provide all of the same functionalityas described above with respect to the medicine display 900.

FIG. 12 illustrates example prescription drug package indicators thatmay be displayed in the medicine displays 900 or 1100 in accordance withan example embodiment. As discussed above, a days remaining indicator,doses remaining indicator, refills remaining indicator, prescriptiondrug adherence indicator, and/or prescription drug dose reminder may beprovided in the medicine display 900.

For example, the prescription drug package indicator 1202 may includethe days remaining indicator 1204. The days remaining indicator 1204 mayindicate that the member has 10 days worth of the prescription drugremaining. Further, the prescription drug package indicator 1202 mayinclude the doses remaining indicator 1206, which may indicate that themember has 20 doses remaining.

Additionally, the prescription drug package indicator 1208 may includethe refills remaining indicator 1210. The refills remaining indicator1210 may indicate that the member has 2 refills of the prescription drugleft. Also, the prescription drug package indicator 1208 may include thedoses remaining indicator 1212, which may indicate that the member has90 doses remaining. In some embodiments, the prescription drug packageindicator 1208 may include the prescription drug dose reminder 1214. Theprescription drug dose reminder 1214 may remind the member to take adose of the prescription drug.

In some embodiments, synergies may be created between various types ofdata received through the medicine display. For example, memberadherence data, lab data, and clinical data may be connected and may beused to provide the member with enhanced health care service. Throughthe medicine display, the member may connect with the PBM, doctor,caregiver, or pharmaceutical manufacturer to provide feedback andreceive enhanced care. The member data collected may be used to identifyprescription drug adherence problems, identify potential conversionopportunities, or shape client formularies. The members that activelyuse reminders, report usage, and adhere to therapy could receive lowercopays while non-adhering members might be placed into more constrainedplans, step therapy, or prior authorization to encourage therapyadherence.

In some embodiments, regular reports may be provided to the member tohighlight how well they are doing, yearly savings, or health goals. Forexample feedback through the medicine display may be tied in withclinical and lab reporting to show how adherence may affect outcomes,such as lower cholesterol or blood pressure improvement.

While a number of different types of user interface elements have beenreflected above, other types of user interface elements may be used torepresent different display elements.

FIG. 13 shows a block diagram of a machine in the example form of acomputer system 1300 within which a set of instructions may be executedcausing the machine to perform any one or more of the methods,processes, operations, or methodologies discussed herein. The mobileelectronic device 102 or the benefit manager device 106 may include thefunctionality of the one or more computer systems 1300.

In an example embodiment, the machine operates as a standalone device ormay be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a server computer, a client computer, a personal computer(PC), a tablet PC, a gaming device, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, anetwork router, switch or bridge, or any machine capable of executing aset of instructions (sequential or otherwise) that specify actions to betaken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The example computer system 1300 includes a processor 1302 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) or both),a main memory 1304 and a static memory 1306, which communicate with eachother via a bus 1308. The computer system 1300 further includes a videodisplay unit 1310 (e.g., a liquid crystal display (LCD) or a cathode raytube (CRT)). The computer system 1300 also includes an alphanumericinput device 1312 (e.g., a keyboard), a cursor control device 1314(e.g., a mouse), a drive unit 1316, a signal generation device 1318(e.g., a speaker) and a network interface device 1320.

The drive unit 1313 includes a computer-readable medium 1322 on which isstored one or more sets of instructions (e.g., software 1324) embodyingany one or more of the methodologies or functions described herein. Thesoftware 1324 may also reside, completely or at least partially, withinthe main memory 1304 and/or within the processor 1302 during executionthereof by the computer system 1300, the main memory 1304 and theprocessor 1312 also constituting computer-readable media.

The software 1324 may further be transmitted or received over a network1326 via the network interface device 1320.

While the computer-readable medium 1322 is shown in an exampleembodiment to be a single medium, the term “computer-readable medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“computer-readable medium” shall also be taken to include any mediumthat is capable of storing or encoding a set of instructions forexecution by the machine and that cause the machine to perform any oneor more of the methodologies of the present invention. The term“computer-readable medium” shall accordingly be taken to include, butnot be limited to, solid-state memories, and optical media, and magneticmedia. In some embodiments, the computer-readable medium is anon-transitory computer-readable medium.

The terms “based upon”, “based on”, “at least in part”, or “including”as used herein, may reflect an open-ended term or function that canreflect other elements or functions beyond those that may be explicitlyrecited.

The terms “a”, “an”, or “the”, as used herein, may reflect either asingle element or multiple elements when one of the terms precedes anelement of the methods or systems described herein.

While the methods and systems described herein generally reflectinterfacing with a member of a prescription drug plan, the methods andsystems may also interface with a member of a health plan, a non-memberpatient of a pharmacy, or the like. The methods and systems may alsointerface with other types of persons.

While the methods and systems described herein generally reflect the useof a mobile electronic device, other types of devices includingnon-mobile electronic devices may be used.

Certain systems, apparatus, applications or processes are describedherein as including a number of modules. A module may be a unit ofdistinct functionality that may be presented in software, hardware, orcombinations thereof. When the functionality of a module is performed inany part through software, the module includes a computer-readablemedium. The modules may be regarded as being communicatively coupled.

The inventive subject matter may be represented in a variety ofdifferent embodiments of which there are many possible permutations.

In an example embodiment, prescription drug data associated with aprescription drug may be accessed. The prescription drug may beassociated with a member. The prescription drug data may includeprescription name data, prescription packaging data, prescription pilldata, and dosage data. A prescription pill indicator and a prescriptionpackage indicator may be determined based on the prescription drug data.A medicine display may be generated based on the prescription drug dataassociated with the prescription drug. The medicine display may includethe prescription pill indicator in association with the prescriptionpackage indicator, a prescription name indicator, and a dosageindicator. The prescription name data, the prescription packaging data,and the prescription pill data may be associated with the prescriptiondrug and the dosage data may be associated with the member.

In an example embodiment, a first drug and a second drug may beidentified. The first drug and the second drug may be associated with amember. Pill image data associated with the first drug and the seconddrug may be accessed. Pill dosage data associated with the first drugand the second drug may also be accessed. Further, a pill box displaymay be generated based on the pill image data and the pill dosage data.The pill box display may include a first pill image indicatorcorresponding to the first drug. The pill box display may also include asecond pill image indicator corresponding to the second drug.

Thus, methods and systems for graphical medicine display have beendescribed. Although embodiments of the present invention have beendescribed with reference to specific example embodiments, it will beevident that various modifications and changes may be made to theseembodiments without departing from the broader spirit and scope of theembodiments of the invention. Accordingly, the specification anddrawings are to be regarded in an illustrative rather than a restrictivesense.

The methods described herein do not have to be executed in the orderdescribed, or in any particular order. Moreover, various activitiesdescribed with respect to the methods identified herein can be executedin serial or parallel fashion. Although “End” blocks are shown in theflowcharts, the methods may be performed continuously.

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims.

In addition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject mattermay lie in less than all features of a single disclosed embodiment.Thus, the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment.

What is claimed is:
 1. A method comprising: accessing, on a processor,prescription drug data associated with a prescription drug, theprescription drug being associated with a member, the prescription drugdata including prescription name data, prescription packaging data,prescription pill data, and dosage data; determining, on the processor,a prescription pill indicator and a prescription package indicator basedon the prescription drug data; generating, on the processor, a medicinedisplay based on the prescription drug data associated with theprescription drug, the medicine display including an image of theprescription package indicator and the prescription pill indicatorassociated with the prescription package indicator, a prescription nameindicator, and a dosage indicator, wherein the prescription name data,the prescription packaging data, and the prescription pill data areassociated with the prescription drug and the dosage data is associatedwith the member; accessing prescription drug label data associated withthe prescription drug and the member; generating a prescription druglabel indicator based on the prescription drug label data, the medicinedisplay including the prescription drug label indicator and a graphicalrepresentation of a medicine cabinet, the prescription pill indicatorbeing located within the graphical representation of the medicinecabinet, wherein generating includes collecting ratings data from apharmacy benefit plan member through the medicine cabinet by presentinga ratings popup sub-display with selectable items on top of the medicinecabinet and reporting the collected ratings data to a prescriber device;accessing an indication that at least one of the following is changed:(i) the prescription drug label data and the prescription packagingdata; updating the prescription drug label indicator and theprescription package indicator in the medicine cabinet based on theindication that the prescription drug label data changed or that theprescription packaging data changed, respectively; and selecting adisplayed prescription package indicator to drag the selectedprescription package indicator to a location in the medicine cabinet atwhich at least one of a price, information, addition or deletion for theprescription drug will be provided by a pharmacy benefit plan device. 2.The method of claim 1, further comprising: determining a number of daysremaining for the member to consume the prescription drug based on theprescription drug data and the dosage data; and generating a daysremaining indicator corresponding to the number of days remaining forthe member to consume the prescription drug, wherein the medicinedisplay includes the days remaining indicator displayed with theassociated image of the prescription package indicator.
 3. The method ofclaim 1, further comprising: determining a number of doses of theprescription drug remaining for the member based on the prescriptiondrug data and the dosage data; and generating a doses remainingindicator corresponding to the number of doses of the prescription drugremaining for the member, wherein the medicine display includes thedoses remaining indicator displayed with the image of the prescriptionpackage indicator for the prescription drug.
 4. The method of claim 1,further comprising: determining a number of refills of the prescriptiondrug remaining for the member based on the prescription drug data andthe dosage data; and generating a refills remaining indicatorcorresponding to the number of refills of the prescription drugremaining for the member, wherein the medicine display includes therefills remaining indicator.
 5. The method of claim 1, furthercomprising: preloading dosage instructions associated with theprescription drug based on the dosage data; and loading a plurality ofdose reminders associated with the prescription drug into an electroniccalendar, the electronic calendar being associated with the member. 6.The method of claim 1, wherein the prescription drug label indicatorincludes a photograph of a label associated with the prescription drugbefore fulfillment of a prescription drug order to the member, andwherein the photograph of a label is displayed as part of the image ofthe prescription package indicator on a member device.
 7. The method ofclaim 1, further comprising: accessing an indication that theprescription drug label data changed; and updating the prescription druglabel indicator in the medicine display based on the indication that theprescription drug label data changed.
 8. The method of claim 1, furthercomprising: accessing prescription drug expiration data associated withthe prescription drug and the member; and generating a prescription drugexpiration indicator based on the prescription drug expiration data,wherein the medicine display includes the prescription drug expirationindicator.
 9. The method of claim 1, wherein the medicine displayincludes a prescription drug dose reminder indicating that the memberfollow a prescription drug dosage associated with the prescription drugand the member, the prescription drug dose reminder based on theprescription drug data and the dosage data.
 10. The method of claim 1,further comprising: receiving a member dose indication, the member doseindication corresponding to whether the member followed a prescriptiondrug dosage associated with the prescription drug; determining aprescription drug adherence metric based on the prescription drug dataand the dosage indicator; and generating a prescription drug adherenceindicator based on the prescription drug adherence metric, wherein themedicine display includes the prescription drug adherence metric. 11.The method of claim 1, further comprising: accessing an indication thatthe prescription packaging data changed; and updating the prescriptionpackage indicator in the medicine display based on the indication thatthe prescription packaging data changed.
 12. The method of claim 1,wherein the prescription package indicator includes a photograph ofpackaging associated with the prescription drug before fulfillment of aprescription drug order to the member.
 13. The method of claim 1,further comprising: comparing a prescription drug image associated withthe prescription drug data with a standard prescription drug imageassociated with the prescription drug to determine that there is a drugmatch, wherein the prescription package indicator is included in themedicine display based on the drug match.
 14. The method of claim 1,wherein the prescription pill indicator visually represents theprescription drug having been prescribed to the member and theprescription package indicator visually represents packaging in whichthe prescription drug was packed when provided to the member.
 15. Anon-transitory machine-readable medium comprising instructions, whichwhen executed by one or more processors, cause the one or moreprocessors to perform the following operations: access, on a processor,prescription drug data associated with a prescription drug, theprescription drug being associated with a member, the prescription drugdata including prescription name data, prescription packaging data,prescription pill data, and dosage data; determine, on the processor, aprescription pill indicator and a prescription package indicator basedon the prescription drug data; access prescription drug label dataassociated with the prescription drug and the member; determine, on theprocessor, a prescription drug label indicator based on the prescriptiondrug label data; and generate, on the processor, a medicine displaybased on the prescription drug data associated with the prescriptiondrug, the medicine display including the prescription pill indicator inassociation with the prescription package indicator, a prescription nameindicator, a dosage indicator, the prescription drug label indicator anda graphical representation of a medicine cabinet, the prescription pillindicator being located within the graphical representation of themedicine cabinet; wherein the prescription name data, the prescriptionpackaging data, and the prescription pill data are associated with theprescription drug and the dosage data is associated with the member,wherein generating, on the processor, the medicine display includescollecting ratings data from a pharmacy benefit plan member through themedicine cabinet by presenting a ratings popup sub-display withselectable items on top of the medicine cabinet and reporting thecollected ratings data to a prescriber device; wherein generatingincludes generating a full medicine display and a mobile device display,the mobile device display showing a full image of a single prescribeddrug including the prescription pill indicator, the prescription packageindicator, the prescription name indicator, and a dosage indicator, andthe full medicine display including a plurality of prescribed drugs andaction indicators including an add indictor, a trash indicator and aprice indicator; access an indication that the prescription drug labeldata changed and that the prescription packaging data changed; updatethe prescription drug label indicator and the prescription packageindicator in the medicine cabinet based on the indication that theprescription drug label data changed and that the prescription packagingdata changed respectively; and select a displayed prescription packageindicator to drag the selected prescription package indicator to alocation in the medicine cabinet at which at least one of a price,information, addition or deletion for the prescription drug will beprovided by a pharmacy benefit plan device.
 16. A system comprising: aprocessor and a memory coupled to the processor; a data access moduledeployed in the memory and executed by the processor to accessprescription drug data associated with a prescription drug and to accessprescription drug label data associated with the prescription drug and amember, the prescription drug being associated with the member, theprescription drug data including prescription name data, prescriptionpackaging image data, prescription pill data, and dosage data; anindicator determination module deployed in the memory and executed bythe processor to determine a prescription pill indicator and aprescription package indicator based on the prescription drug data andto determine a prescription drug label indicator based on theprescription drug label data; a display generation module deployed inthe memory and executed by the processor to generate a medicine displaybased on the prescription drug data associated with the prescriptiondrug, the medicine display including: the prescription pill indicator inassociation with the prescription package indicator, a prescription nameindicator, a dosage indicator, a prescription drug label indicator, anda graphical representation of a medicine cabinet, the prescription pillindicator being located within the graphical representation of themedicine cabinet, the display generation module collects ratings datafrom a pharmacy benefit plan member through the medicine display bypresenting a ratings popup sub-display with selectable items on top ofthe medicine display and reporting the collected ratings data to aprescriber device; wherein the prescription name data, the prescriptionpackaging image data, and the prescription pill data are associated withthe prescription drug and the dosage data is associated with the member;a change module to access a change indication that at least one of theprescription packaging data, the prescription pill data, or both havechanged, update the prescription package indicator, prescription pillindicator, or both in the medicine display based on the changeindication at least one of the prescription packaging data, theprescription pill data, or both have changed; wherein the data accessmodule is further configured to access an indication that theprescription drug label data changed and that the prescription packagingdata changed; wherein the display generation module is furtherconfigured to update the prescription drug label indicator and theprescription package indicator in the medicine cabinet based on theindication that the prescription drug label data changed and that theprescription packaging data changed respectively; and wherein thedisplay module is configured to provide selection a displayedprescription package indicator to drag the selected prescription packageindicator to a location in the medicine cabinet at which at least one ofa price, information, addition or deletion for the prescription drugwill be provided by a pharmacy benefit plan device.
 17. A methodcomprising: accessing, on a processor, prescription drug data associatedwith a prescription drug, the prescription drug being associated with amember of a pharmacy benefit plan, the prescription drug data includingprescription name data, prescription packaging data, prescription pilldata and dosage data stored in a pharmacy benefit plan device;determining, on the processor, a prescription pill indicator and aprescription package indicator based on the prescription drug data froma database of the pharmacy benefit plan device, the prescription pillindicator visually representing the prescription drug having beenprescribed to the member and the prescription package indicator visuallyrepresenting packaging in which the prescription drug was packed whenprovided to the member; determining a number of days remaining for themember to consume the prescription drug based on the prescription drugdata and the dosage data; generating a days remaining indicatorcorresponding to the number of days remaining for the member to consumethe prescription drug; determining a number of refills of theprescription drug remaining for the member based on the prescriptiondrug data and the dosage data; generating a refills remaining indicatorcorresponding to the number of refills of the prescription drugremaining for the member; accessing prescription drug label dataassociated with the prescription drug and the member; generating aprescription drug label indicator based on the prescription drug labeldata, the prescription drug label indicator including a photograph of alabel associated with the prescription drug before fulfillment of aprescription drug order of the prescription drug to the member;generating, on the processor, a medicine display based on theprescription drug data associated with the prescription drug, themedicine display including the prescription pill indicator inassociation with the prescription package indicator, a prescription nameindicator, a dosage indicator, the days remaining indicator, the refillsremaining indicator, and the prescription drug label indicator, themedicine display includes a graphical representation of a medicinecabinet, the prescription pill indicator, the prescription packageindicator, the prescription name indicator, the dosage indicator, thedays remaining indicator, the refills remaining indicator, and theprescription drug label indicator being located within the graphicalrepresentation of the medicine cabinet wherein generating, on theprocessor, the medicine display includes collecting ratings data from apharmacy benefit plan member through the medicine cabinet by presentinga ratings popup sub-display with selectable items on top of the medicinecabinet and reporting the collected ratings data to a prescriber device;accessing an indication that the prescription drug label data changedand that the prescription packaging data changed; updating theprescription drug label indicator and the prescription package indicatorin the medicine cabinet based on the indication that the prescriptiondrug label data changed and that the prescription packaging data changedrespectively; and selecting a displayed prescription package indicatorto drag the selected prescription package indicator to a price locationin the medicine cabinet at which a price for the prescription drug willbe provided by the pharmacy benefit plan device.
 18. The method of claim17, wherein generating, on the processor, the medicine display includesorganizing the prescription pill indicator by therapy to the pharmacybenefit plan member.
 19. The method of claim 17, further comprisingsending ratings data, the days remaining indicator, and the refillsremaining indicator from the pharmacy benefit plan member through themedicine cabinet to the pharmacy benefit plan device and computing aconversation opportunity related to the member at the pharmacy benefitplan device.
 20. The method of claim 17, wherein generating, on theprocessor, the medicine display includes generating an add indicator onwhich a displayed prescription package indicator can be dragged to anddropped on to order a refill of a prescription medicine associated withthe displayed prescription package indicator, and generating a trashindicator on which the displayed prescription package indicator can bedragged to and dropped on to remove the displayed prescription packageindicator from the medicine cabinet.
 21. The method of claim 17, whereingenerating, on the processor, the medicine display includes generating aprice indicator on which a displayed prescription package indicator canbe dragged to and dropped on to request pricing from a prescriptionbenefit manager device, and generating an information indicator on whichthe displayed prescription package indicator can be dragged to anddropped on to request drug data for the prescription associated with thedisplayed prescription package indicator from a remote server.
 22. Themethod of claim 17, wherein generating a mobile medicine cabinet displayincludes generating a complete graphic user interface of a singlecomplete combination of the prescription package indicator and theprescription pill indicator with selectable icons to scroll through themedicine cabinet on a mobile device.
 23. The method of claim 22, whereingenerating a mobile medicine cabinet display includes generating partialviews of the prescription package indicator and the prescription pillindicator when they precede or follow the complete graphic userinterface of the single complete combination of the prescription packageindicator and the prescription pill indicator.
 24. The method of claim17, wherein generating the medicine display includes displaying theprescription pill indicator in front of the prescription packageindicator, wherein generating the medicine display includes generating amobile medicine cabinet display using the graphical representation ofthe medicine cabinet for display on a mobile device and includesgenerating a non-mobile medicine cabinet display using the graphicalrepresentation of the medicine cabinet for display on a non-mobiledevice.